fix: use lockfile-aware install commands#1179
Merged
Merged
Conversation
crazy-max
changed the title
crazy-max
approved these changes
Jun 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was generated by
sec-cli github repositories npm-ci update.What changed
Bare install commands were replaced with lockfile-aware equivalents:
yarn installyarn install --immutableWhy
Using lockfile-aware install commands (
npm ci,--frozen-lockfile,--immutable) ensures that CI builds use exactly the dependency versionspinned in the lockfile, making builds reproducible and preventing
unintended dependency upgrades during install.